Systems and methods for onboarding customers through a short-range communication channel

ABSTRACT

Systems, methods, and apparatuses for enrolling a user with a product of a financial institution. A computing device associated with a financial institution includes a network interface enabling the computing device to exchange information over a network, one or more processors, and non-transitory machine-readable media storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations. The operations include establishing a short-range communication channel with a user device associated with a user based on a tap exchange and receiving personal information from the user device over the short-range communication channel. The personal information is associated with an enrollment of the user with a product of the financial institution. The operations further include providing the personal information to a computing system associated with the financial institution to enroll the user with the product.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No.15/395,187, filed Dec. 30, 2016, which claims the benefit of andpriority to U.S. Provisional Application No. 62/317,211, filed Apr. 1,2016, both of which are incorporated herein by reference in theirentireties.

TECHNICAL FIELD

Embodiments of the present disclosure relate to systems and methods toonboard customers to facilitate account enrollment.

BACKGROUND

Currently, financial institutions enroll customers in one or more oftheir products daily (e.g., a demand deposit account, etc.). Inpractice, the customer must typically visit a branch location associatedwith the financial institution and fill out a substantial amount ofpaperwork in order to enroll. Not only is such a process time-consumingand labor-intensive, such a process is prone to errors (e.g.,typographical) and typically unpleasant for the customer. Accordingly,better systems and methods are needed for enrolling or onboardingcustomers.

SUMMARY

A first example embodiment relates to an apparatus. The apparatusincludes a personal information database structured to store personalinformation regarding a user associated with a user device; and, acommunication circuit communicably coupled to a network interface of theuser interface. According to one embodiment, the communication circuitis structured to: establish a short-range communication channel with anearby financial institution computing device based on a tap exchange;and selectively transmit personal information from the personalinformation database to the financial institution computing device overthe short-range communication channel to enroll the user with a productof a financial institution associated with the financial institutioncomputing device.

Another example embodiment relates to a mobile device. The mobile deviceincludes a processor; and, a non-transitory computer readable mediumstoring instructions, which when executed causes the processor toperform a method. According to one embodiment, the method includes:establishing a short-range communication channel with a financialinstitution computing device based on a tap exchange; retrievingpersonal information stored in a personal information database regardinga user of the mobile device; and selectively transmitting the personalinformation from the personal information database to the financialinstitution computing device to enroll the user with a product of afinancial institution associated with the financial institutioncomputing device.

Another example embodiment relates to a method. The method includesestablishing, by a network interface of a mobile device, a short-rangecommunication channel with a financial institution computing devicebased on a tap exchange; receiving, by an account enrollment circuit ofthe mobile device, a request for personal information from the financialinstitution computing device; receiving, by a graphical user interfaceof the mobile device, an authorization to transmit the requestedpersonal information; retrieving, by the account enrollment circuit, thepersonal information from a personal information database of the accountenrollment circuit; and transmitting, by the network interface, thepersonal information to enroll the user with a product of a financialinstitution, the financial institution associated with the financialinstitution computing device.

These and other features, together with the organization and manner ofoperation thereof, will become apparent from the following detaileddescription when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a diagram of a financial institution environment, according toan example embodiment.

FIG. 2 is a schematic diagram of a computing system, according to anexample embodiment.

FIG. 3 is a diagram of a user device of the computing system of FIG. 2,according to an example embodiment.

FIG. 4 is a diagram of synced graphical user interfaces of a user deviceand a financial institution computing device, according to an exampleembodiment.

FIG. 5 is a flow diagram of a method of onboarding or enrolling acustomer with a financial institution via a short-range communicationchannel, according to an example embodiment.

DETAILED DESCRIPTION

Referring to the Figures generally, systems, methods, and apparatusesfor enrolling or onboarding customers with a financial institutionthrough a short-range communication channel are shown and describedherein. According to the present disclosure, a user device (e.g., mobilephone) may include an account enrollment application having an accountenrollment circuit. The account enrollment circuit may at leastpartially be disposed in a secure element (e.g., secure memory storage)of the user device, when the user device is equipped with a secureelement. If the user device is not equipped with a secure element, theaccount enrollment circuit may be at least partially disposed in amemory device of the user device and/or in a cloud environment (e.g., aserver-based infrastructure) communicably coupled to the user device. Inany of the above configurations, the account enrollment circuit mayinclude a person information database structured to store personal orconfidential information regarding the user (e.g., social securitynumber, address, phone number, next of kin, beneficiaries, etc.), aninput/output circuit, and a communication circuit. The input/outputcircuit may enable the exchange of information with the user (e.g., viathe graphical user interface of the user device). The communicationcircuit may be structured to establish or facilitate establishment of ashort-range communication channel with a computing device of thefinancial institution (i.e., a financial institution computing device).After establishment, the communication circuit may selectively providepersonal information from the personal information database to thefinancial institution computing device. In response, the financialinstitution computing device may populate an account registrationform(s) to enroll or onboard the customer with the financialinstitution. Simultaneously or nearly simultaneously, the accountenrollment circuit may provide an account enrollment application on theuser device that allows the user to observe and modify informationprovided to the financial institution computing device. In this regard,the user may be able to confirm or deny accuracy of personalinformation.

Beneficially, the account enrollment circuit facilitates a relativelyfaster enrollment process than manually filling out paperwork. Further,the account enrollment circuit reduces or alleviates the likelihood oftranscription errors by providing personal information received directlyfrom the user (as compared to an attendant at the financial institutionlistening to the user and transcribing the user's information). Further,by electronically providing the enrollment information, the financialinstitution may update their accounts database or other relevant storagelocation relatively faster than relying on manual transmission by theattendant. In this regard, the customer may engage or utilize one ormore financial products of the financial institution relatively fasterthan in conventional systems.

Technically and advantageously, the account enrollment circuittransforms operation of the user device by storing and selectivelyproviding personal information regarding the user. Typically, the useror customer shields their personal information from exposure and, manypeople may feel wary of having this information stored on a mobiledevice (e.g., a smartphone) because of the potentiality of the mobiledevice being hacked or the user losing the mobile device. By storing theperson information in either a cloud environment or in a secure element,the mobile device may provide functionality and security that waspreviously inexistent. As a result, operation of the mobile device istransformed to realize previously inexistent functionality.

Moreover, by utilizing a short-range communication channel (e.g.,Bluetooth, near-field communication (NFC), etc.), the systems, methods,and apparatuses of the present disclosure transform traditionalenrollment processes into a relatively secure and efficient process. Inthis regard, the short-range communication channel restricts thedistance that the customer and financial institution computing devicecan be apart to still enable enrollment. As such, the ability forfraudsters to intercept these communications may be reduced. Thus, thesystems, methods, and apparatuses of the present disclosure may providesecure and relatively fast wireless enrollment processes.

As used herein, the terms “enrollment” and “on-boarding” are usedinterchangeably to refer to registration or sign-up for one or morefinancial institution products (e.g., open a checking or savingsaccount, etc.). According to one embodiment, the enrollment oron-boarding refers to a first-time enrollment process for the user witha specific financial institution. In this regard, the financialinstitution does not have a previous record regarding the user. However,the principles of the present disclosure may also be applicable withsubsequent enrollments (e.g., an application for a loan at the financialinstitution where the user has an existing demand deposit account). Inthis regard, the information stored in the personal information database(described below) may be richer than that stored in the financialinstitution computing system. As such, the systems, methods, andapparatuses of the present disclosure are applicable with bothfirst-time and non-first time enrollments.

It should be understood that the term “product” as associated with afinancial institution refers to a service or product offered by thefinancial institution and, as such, and may be highly variable. Forexample, a non-exhaustive list of financial institution “products”includes, but is not limited to: a demand deposit account (e.g., achecking account, a savings account, etc.), a mortgage application, acertificate of deposit account, a money market account, an individualretirement account, and a loan application (e.g., a student loanapplication, a private loan, etc.). Thus, the “product” of the financialinstitution is meant to be broadly interpreted herein. In this regardand as described herein below, the “financial institution” may be highlyconfigurable as well, with all such variations intended to fall withinthe scope of the present disclosure.

Referring now to FIG. 1, a diagram of a financial institutionenvironment is depicted, according to an example embodiment. As shown,an interior physical location (i.e., brick and mortar) of a financialinstitution 10 is depicted. The financial institution 10 is shown toinclude an attendant 20 utilizing a financial institution computingdevice 30 and a user 40 (also referred to as a customer herein)utilizing a user device 50, shown as a smartphone. The financialinstitution 10 may include any type of financial institution including,but not limited to, a bank, a credit union, and the like. It should beunderstood that while the present disclosure describes on-boarding andenrollment in regard to financial institutions that this description isnot meant to be limiting. In this regard, the present disclosure may beapplicable with any enrollment process done in person where confidentialinformation is exchanged. For example, the present disclosure may beapplicable in a mortgage company setting to, e.g., fill out a mortgageapplication. In another example, the present disclosure may beapplicable in a student loan company setting to fill out a student loanapplication. Thus, the principles contained herein are meant to bebroadly interpreted.

The financial institution computing device 30 may include any type ofcomputing device used by financial institution attendants that iscapable of a short-range communications. Accordingly, the financialinstitution computing device 30 may include, but is not limited to, amobile phone (e.g., smart phone), tablet computer, a personal computer,and any other computing device. In the example shown, the computingdevice 30 is structured as tablet computer. Similarly, the user device50 may include any type of mobile device of a user 40 including, but notlimited to, a phone (e.g., a smartphone, etc.) and a computing device(e.g., a tablet computer, a laptop computer, a person digital assistant,etc.).

In operation, the user 40 may “tap” the user device 50 with thefinancial institution computing device 30 to establish a short-rangecommunication channel 60. As used herein, the term “tap” refers to aninitial pairing or pairing process of the mobile device 50 with thefinancial institution computing device 30 to establish a short-rangecommunication channel (e.g., short-range communication channel 60). Inthis regard and in one embodiment, the “tap” is a NFC tap. In anotherembodiment, the “tap” is a Bluetooth communication protocol pairingprocess. In either embodiment, the “tap” may also include various otheradditional security protocols (e.g., passcodes, biometrics, etc.) thataugment the “tap” to ensure or substantially ensure that the tap wasintended between each of the user device 50 and the financialinstitution computing device 30.

In one embodiment, the communication channel 60 may comprise solely theBluetooth communication protocol. As an example, the user 40 mayinitiate a Bluetooth communication protocol on their mobile device 50.The attendant 20 may initiate a Bluetooth communication protocol on thefinancial institution computing device 30. Upon locating the computingdevice 30, the financial institution computing device 30 may pair withthe user device 50 (i.e., the “tap” in this example) to enable theexchange of information. As explained herein and due to the relativesensitivity of the personal information, the user 40 and/or financialinstitution attendant 20 may configure their settings to prohibitautomatic coupling after an initial pairing of the devices.

In another embodiment, the communication channel 60 may comprise solelythe NFC protocol. While the Bluetooth communication protocol typicallyrequires an initial pairing of devices, the NFC protocol typically doesnot. However, the NFC protocol is limited to only being applicable inshort proximity (e.g., typically within four inches of each device).Once in range, the user device 50 and the computing device 30 may beginto exchange information over the communication channel 60. Beneficially,using NFC, the user device 50 and computing device 30 may be required tobe in close proximity for the duration of the communication, which mayact as an added layer of security during the on-boarding process.

In still another embodiment, the communication channel 60 may comprise acombination of NFC and Bluetooth communication protocols. As an example,the user device 50 and computing device 30 may tap via the NFC protocolto exchange authentication information. The user 40, via a graphicaluser interface on the mobile device 120, may receive and observe arequest from the computing device 30 to establish a link (e.g., thecommunication channel). Upon reception of an acceptance or approval ofthe request, the user device 50 and/or the computing device 30 mayprovide a “handover request,” the handover request structured to enableBluetooth pairing between the devices 50 and 30 to enable exchange ofinformation over the Bluetooth communication protocol.

Beneficially, using a NFC tap to initiate pairing followed by Bluetoothdata transmission enables relatively more security in the communicationsbetween the user device 50 and the financial institution computingdevice 30 because of the requirement of the NFC tap (i.e., that thedevices 30 and 50 be in NFC proximity to each other).

It should be understood that the three short-range communicationchannels that represent the communication channel 60 described above arenot meant to be limiting as the present disclosure contemplates any andall other types of short range communication channels that are intendedto fall within the scope of the present disclosure. As described herein,after establishment of the communication channel 60, the user device 50and the computing device 30 may exchange information to enableonboarding of the user 40 with the financial institution 10.

Referring now to FIG. 2, a block diagram of a computing system 200 isshown according to an example embodiment. The computing system 200 mayschematically represent the components of FIG. 1, according to anexample embodiment. As described herein, the computing system 200 mayenable a tap connection between a user device 50 of a user 40 and acomputing device 30 of an attendant 20 of a financial institution 10 toinitiate establishing a communication channel 60 that is relativelysecure to allow the exchange of personal information of the user 40 tothe financial institution computing device 30 to facilitate a relativelyquick enrollment of the user 40 with the financial institution 10. Asshown, the computing system 200 includes one or more user devices 50associated with a user 40, one or more financial institution computingdevices 30 associated with an attendant 20 of the financial institution10, and a financial institution computing system 240 associated with thefinancial institution 10. The user device 50, financial institutioncomputing device 30, and financial institution computing system 240 maybe communicably and operatively coupled over a network 202. The network202 may be any type of type of network. For example, the network 202 maybe a wireless network interface (e.g., 802.11X, ZigBee, Internet, WI-FI,etc.), a wired network interface (e.g., Ethernet), or any combinationthereof. The network 202 is structured to permit the exchange of data,values, instructions, messages, and the like between and among the userdevice 50, financial institution computing device 30, and the financialinstitution computing system 240.

As shown, the user device 50 and the financial institution computingdevice 30 may be communicably and operatively coupled to a cloud 260.The cloud 260 refers to a computing style where computing resourcesincluding, but not limited to, server components including processors,storage or memory components, application programs, and the like arestored in one or more remote locations and provided over a network, suchas network 202, to a device upon request (such as to the user device50). In this regard, the cloud 260 may also be referred to as acloud-based server herein. Beneficially, such a structure enables thedevice to have or store relatively less native applications to, in turn,improve processing speed. Further, by storing data in the cloud 260, theuser 40 may access that data from one or more different user devices 50.

As also shown, the financial institution 10 includes a financialinstitution computing system 240. The financial institution computingsystem 240 includes a processor 242 and a memory device 244. Theprocessor 242 may be implemented as a general-purpose processor, anapplication specific integrated circuit (ASIC), one or more fieldprogrammable gate arrays (FPGAs), a digital signal processor (DSP), agroup of processing components that may or may not be geographicallydispersed (e.g., situated in various locations to form a server-basednetwork), or other suitable electronic processing components. The one ormore memory devices 244 (e.g., RAM, ROM, NVRAM, Flash Memory, hard diskstorage, etc.) may store data and/or computer code for facilitating atleast some of the various processes described herein. In this regard,the memory 244 may store programming logic that, when executed by theprocessor 242, control the operation of the financial institutioncomputing system 240.

As shown, the financial institution computing system 240 includes anetwork interface 246. The network interface 246 facilitates the sendingand receiving of data over the network 202 (e.g., to and from the userdevice 50, etc.). The financial institution computing system 240 mayalso include an accounts database 248 that stores customer informationand account information relating to accounts held with the financialinstitution 10 of various customers.

As mentioned above, the attendant 20 may be associated with or have oneor more computing devices 30 (i.e., the “financial institution computingdevice”). The attendant 20 may be any representative of the financialinstitution 10 (e.g., a teller, banker, etc.) who may facilitateon-boarding for the user 40. As also mentioned above, the computingdevice 30 may include any type of computing device capable ofestablishing a short-range communication channel 60. Thus, and asmentioned above, the financial computing device 30 may include a tabletcomputer, a smartphone, and the like.

As shown, the financial computing device 30 includes a processor 250, amemory 252 communicably coupled to the processor 250, and a networkinterface 254. The memory 252 may store instructions that, when executedby the processor 250, cause implementation of a routine to facilitateconnecting via the network interface 254 with the user device 50 (andfinancial institution computing system 240). The processor 250 may beimplemented as a general-purpose processor, an application specificintegrated circuit (ASIC), one or more field programmable gate arrays(FPGAs), a digital signal processor (DSP), a group of processingcomponents, or other suitable electronic processing components. The oneor more memory devices 252 (e.g., RAM, ROM, NVRAM, Flash Memory, harddisk storage, etc.) may store data and/or computer code for facilitatingat least some of the various processes described herein, such asfacilitating communicable connection with the user device 50. Thenetwork interface 254 includes any of a cellular transceiver (e.g.,CDMA, GSM, LTE, etc.), a wireless network transceiver (e.g., 802.11X,ZigBee, Bluetooth, etc.), or a combination thereof (e.g., both acellular transceiver and a Bluetooth transceiver). Further, the networkinterface 254 may include cryptography capabilities to establish asecure or relatively secure communication session with the user device50 via the communication channel 60.

As shown in FIGS. 1-2 and mentioned above, the user 40 may have or beassociated with a user device 50. The user 40 may include individuals,business representatives, large and small business owners, and any otherentity. The user may also be referred to as the customer herein tosignify that the customer or user 40 may be new to the financialinstitution 10. Hence, the user 40 may be enrolling with the financialinstitution 10 to receive or utilize one or more financial institutionproducts (e.g., establishment of a demand deposit account). The userdevice 50 may be generally described as a mobile device 210. The mobiledevice 210 may include any wearable device. Wearable devices refer toany type of device that a user wears including, but not limited to, awatch (e.g., a smart watch), glasses (e.g., eye glasses, sun glasses,smart glasses, etc.), bracelet (e.g., a smart bracelet), etc. The mobiledevice 210 may also include any type of mobile device of a user 40including, but not limited to, a phone (e.g., a smartphone, etc.) and acomputing device (e.g., a tablet computer, a laptop computer, a persondigital assistant, etc.). Accordingly, the user device 50 may include adisplay device (e.g., a screen) and one or more input/output devices(e.g., a touch screen, microphone, speaker, keyboard, etc.).

In this example, the user device 50 includes an account enrollmentclient application 220 and a mobile banking client application 230. Inone embodiment, the account enrollment client application 220 and themobile banking client application 230 may be server or cloud 260-basedapplications executable on the user device 50. In this regard, a usermay have to first download the application(s) prior to their usage. Inanother embodiment, the account enrollment client application 220 andthe mobile banking client application 230 may be hard coded into thememory (e.g., memory 303 of user device 50 of FIG. 3). In still anotherembodiment, the account enrollment client application 220 and the mobilebanking client application 230 may be web-based interface applications.In this configuration, the user may have to log onto or access theweb-based interface before usage of the application(s). In this regard,at least one of the account enrollment client applicant application 220and the mobile banking client application 230 may be supported by aseparate computing system comprising one or more servers, processors,network interface modules, etc. that transmit the applications for useto the user device 50. In certain embodiments, the account enrollmentclient application 220 and the mobile banking client application 230 mayinclude an application programming interface (API) and/or a softwaredevelopment kit (SDK) that facilitate the integration of otherapplications with at least one of the account enrollment clientapplication 220 and the mobile banking client application 230. All suchvariations and combinations are intended to fall within the spirit andscope of the present disclosure.

The mobile banking client application 230 may be communicably coupled tothe financial computing system 240 (e.g., the accounts database 248) viathe network 202 and may be structured to permit management of the user'saccounts via the mobile banking client application 230. In this regard,the mobile banking client application 230 may provide displaysindicative of current account balances, pending transactions, profileinformation (e.g., contact information), and the like. Further, in someembodiments, the mobile banking client application 230 may also permitpayments from the user 40 to a designated recipient. For example, themobile banking client application 230 may depict a loan (e.g., amortgage) of a user and allow the user to pay the mortgage from one oftheir accounts (e.g., checking or savings). In another example, a billpay option may be provided by the mobile banking client application 230,where the bill pay option allows the user 40 to pay his/her bills.

The mobile banking client application 230 may be utilized or accessiblefollowing enrollment with the financial institution 10. In this regard,the mobile client application 230 may be executable after the user 40enrolls or on-boards with the financial institution 10. Hence, themobile banking client application 230 may be a product of the financialinstitution 10 that is retrievable, executable, and useable followingregistration or enrollment of the user 40 with the financial institution10.

As shown, the account enrollment client application 220 may becommunicably coupled to a cloud 260. In this regard and as mentionedabove, the account enrollment client application 220 may be either oneof a cloud-based application (where the application must first bedownloaded) or a web-based application (where the user logs onto theapplication over a website). However, in another embodiment, the accountenrollment client application 220 may be completely housed or embodiedwithin the user device 50. This embodiment is described and shown herein in FIG. 3. In still another embodiment, only one or more componentsof the client application 220 may be housed within or included with theuser device 50. For example, the cloud 260 may be structured to includethe personal information database 346 yet the input/output circuit 342and the communication circuit 344 are stored in the user device 50, suchthat confidential or personal information of the user 40 is remotelystored relative to the user device 50. This configuration may bebeneficial when the user device 50 does not include a secure memorydevice, such as the secure element 330 of FIG. 3. Thus, bothembodiments—inclusion of the account enrollment circuit 340 in the userdevice 50 completely or inclusion of the account enrollment circuit 340only partially (e.g., the personal information database 346 is stored inthe cloud 260)—are intended to fall within the spirit and scope of thepresent disclosure. As alluded to above, the structure and function ofthe first embodiment may be explained more fully in regard to FIG. 3.

Accordingly, referring now to FIG. 3, the function and structure of theuser device 50 is shown in greater detail according to an exampleembodiment. As mentioned above, the example of FIG. 3 depicts thecomplete inclusion of the account enrollment circuit 344 with the userdevice 50 as compared to aforementioned other embodiments (e.g., partialinclusion with the user device or that the entire account enrollmentcircuit 344 is remotely located, such as in the cloud 260).

As shown, the user device 50 includes a processing circuit 301 having aprocessor 302 and a memory 303. The processor 302 may be implemented asa general-purpose processor, an application specific integrated circuit(ASIC), one or more field programmable gate arrays (FPGAs), a digitalsignal processor (DSP), a group of processing components, or othersuitable electronic processing components. The one or more memorydevices 303 (e.g., RAM, NVRAM, ROM, Flash Memory, hard disk storage,etc.) may store data and/or computer code for facilitating the variousprocesses described herein. Moreover, the one or more memory devices 303may be or include tangible, non-transient volatile memory ornon-volatile memory. Accordingly, the one or more memory devices 303 mayinclude database components, object code components, script components,or any other type of information structure for supporting the variousactivities and information structures described herein.

The user device 50 is shown to include various circuits, components, andlogic for completing at least some of the activities described herein.More particularly, the user device 50 includes a network interface 310,the mobile banking client application 230 having an account informationcircuit 232, a location circuit 320, and a secure element 330 having theaccount enrollment client application 220 that includes the accountenrollment circuit 340. While various circuits, interfaces, and logicwith particular functionality are shown in FIG. 3, it should beunderstood that the user device 50 may include any number of circuits,interfaces, and logic for completing the functions described herein. Forexample, the activities of multiple circuits may be combined as a singlecircuit, as additional circuits with additional functionality may beincluded, etc.

The network interface 310 is adapted for and structured to establish acommunication session via the network 202 with the financial computingsystem 240. Further, the network interface 310 is structured to alsoestablish the communication channel 60 with the financial institutioncomputing device 30. In this regard and as shown, the network interface310 includes a Bluetooth transceiver 312, a network transceiver 314, anda NFC transceiver 316. The network transceiver 314 may be structured toestablish a communication session over the network 202. Accordingly, thenetwork interface 310 includes any of a cellular transceiver (e.g.,CDMA, GSM, LTE, etc.), a wireless network transceiver (e.g., 802.11X,ZigBee, WI-FI, Internet, etc.), or a combination thereof (e.g., both acellular transceiver). In comparison, the Bluetooth transceiver 312 andthe NFC transceiver 316 are structured to selectively establish aBluetooth communication session (via the Bluetooth transceiver 314) anda NFC communication session (via the NFC transceiver 316) with thefinancial institution computing device 30. The Bluetooth transceiver 312and NFC transceiver 316 may include any components for facilitating andestablishing a communication session via the Bluetooth communicationprotocol and the NFC protocol.

Further, the network interface 310 may include cryptography capabilitiesto establish a secure or relatively secure communication session withthe at least one financial computing system 240 or financial institutioncomputing device 30. In this regard, data may be encrypted to prevent orsubstantially prevent the threat of hacking.

The location circuit 320 may be structured to receive location data anddetermine a location of the user device 50 based on the location data.In one embodiment, the location circuit 320 may include a globalpositioning system (GPS), parts thereof, or any other type of locationpositioning system. As such, the location circuit 320 may receivelatitude data, longitude data, and any other type of location orposition data to determine the location of the user device 50. In otherembodiments, the location circuit 320 may receive an explicit locationidentification from the user of the device 50. All such variations areintended to fall within the spirit and scope of the present disclosure.

As mentioned above, via the mobile banking client application 230, theuser may pay bills (e.g., mortgage, etc.), view balances, and otherwisemanage their account. Accordingly and as shown, the mobile bank clientapplication 230 may include an account information circuit 232. Theaccount information circuit 232 may be linked or otherwise coupled toone or more accounts held by a user and permit management of theassociated account (e.g., transfer balances between accounts, seepayment history, etc.). The mobile banking client application 230 mayalso be communicably coupled to the account enrollment circuit 340. Assuch and as mentioned above, responsive to a successful enrollment ofthe user 40 with the financial institution 10, the mobile banking clientapplication 230 may be utilized and the account information circuit 232activated.

The secure element 330 may be defined as a tamper-resistant componentcapable of hosting and storing confidential information andapplications. In this regard, the secure element 330 may include aremovable smart chip, a fixed chipped in the user device 50, or within aSD card. In other words, the secure element 330 may be configured as achip embedded directly into the user device's 50 hardware, a SIM or UICCcard, or an SD card that can be inserted and removed from the userdevice 50. Thus, the secure element 330 may include relatively moresecurity to resist tampering or hacking. In this regard, the secureelement 330 is shown as separate from the memory device 303. Of course,certain embodiments of the user device 50 may exclude a secure element330. In those embodiments, the account enrollment circuit 340 may besimply included with the user device 50 (e.g., with the memory device303). Thus, the depiction of the user device 50 including a secureelement 330 is intended to show one configuration of the presentdisclosure and not meant to be limiting.

The account enrollment circuit 340 may be structured to generate andprovide the account enrollment client application 220. For example, theaccount enrollment circuit 340 may provide the account enrollment clientapplication 220 as a graphical user interface on the user device 50 (seeFIG. 4). Further and as described herein, the account enrollment circuit340 may be structured to facilitate establishment of a communicationchannel 60 with the financial institution computing device 30 toselectively provide personal information regarding the user to thedevice 30 to onboard the user with the financial institution 10. Asshown, the account enrollment circuit 340 includes an input/outputcircuit 342, a communication circuit 344, and a personal informationdatabase 346, all of which are communicably and operatively coupled toeach other.

The personal information database 346 may be structured to hold, store,or otherwise serve as a repository for personal or confidentialinformation relating to the user 40. Due to the sensitivity of thisdata, the personal information database may be accessible via passcode(e.g., a password, a biometric, etc.) from the user device 50 andaccount enrollment client application 220. Once authenticated, the user40 may populate, add, delete, or otherwise manage the content stored inthe personal information database 346. For example, the personalinformation database 346 may include one or more folders, a searchengine, and the like that make storing and locating various informationmanageable and relatively easy.

The personal or confidential information regarding the user 40 mayinclude any type of personal information regarding the user. In someembodiments, the personal or confidential information may include anytype of information that the user 40 desires to keep stored, yetsubstantially secure. Accordingly, the personal or confidentialinformation may include, but is not limited to, a social securitynumber, a telephone number, a gender, an ethnicity, a height, a weight,a home address, a work address, a work telephone number, a maritalstatus, a name of a beneficiary(ies), a spouse name and other relevantinformation (e.g., social security number), and so on. This informationmay be provided as values that are stored in the database 346. In otherinstances, this information may be provided as files, videos, or anyother suitable manner for storage by the personal information database346. It should be understood that the aforementioned list of personalinformation is not meant to be limiting as the present disclosurecontemplates various other types of personal information that may alsobe stored by the personal information database 346.

The input/output circuit 342 may be structured to receive and providecommunication(s) to a user of the device 50 (or, to another entity suchas the financial institution computing device 30). In this regard, theinput/output circuit 342 may be structured to exchange data,communications, instructions, etc. with an input/output component of thedevice 50. Accordingly, in one embodiment, the input/output circuit 342may include an input/output device such as a display device, atouchscreen, a keyboard, and a microphone. In another embodiment, theinput/output circuit 342 may include communication circuitry forfacilitating the exchange of data, values, messages, and the likebetween an input/output device and the components of the user device 50.In yet another embodiment, the input/output circuit 342 may includemachine-readable media for facilitating the exchange of informationbetween the input/output device and the components of the user device 50(e.g., the resource monetization circuit). In still another embodiment,the input/output circuit 342 may include any combination of hardwarecomponents (e.g., a touchscreen), communication circuitry, andmachine-readable media.

As shown and described herein below, via the input/output circuit 342, auser 40 may provide an input that enables modification, addition, ordeletion of one or more pieces of personal information. Further, viainput/output circuit 342, the user may make adjustments, deletions, andadditions to an electronically generated account registration form tofacilitate onboarding of the user 40.

The communication circuit 344 may be structured to facilitatecommunication with the financial institution computing device 30 toestablish and maintain the communication channel 60. In this regard, thecommunication circuit 344 may be structured to instruct or command thenetwork interface 310 to scan for nearby short-range communicationchannel financial devices (e.g., Bluetooth or NFC capable devices) aswell as instruct the network interface to establish the communicationchannel 60 with the financial institution device 30. Of course, due tothe limited range of the NFC protocol, the scanning for nearby NFCdevices may be based on connecting to a network (e.g., a closed networkwithin the financial institution) that provides a message or indicationto the communication circuit 344 of all or mostly all of the NFC-capabledevices within a particular location. Alternatively, any other means forscanning and/or identifying NFC-capable devices may be implemented andare intended to fall within the scope of the present disclosure.

Accordingly, in one embodiment, the communication circuit 344 includescommunication circuitry for relaying, transmitting, or otherwiseproviding an instruction to the network interface 310 to initiatecommunications with the financial institution computing device 30. Inanother embodiment, the communication circuit 344 includesmachine-readable media for relaying, transmitting, or otherwiseproviding an instruction to the network interface 310 to initiatecommunications with the financial institution computing device 30. Instill another embodiment, the communication circuit 344 includes anycombination of communication circuitry and machine-readable media forrelaying, transmitting, or otherwise providing an instruction to thenetwork interface 310 to initiate communications with the financialinstitution computing device 30.

In one embodiment, the communication circuit 344 is structured tocommand or instruct the network interface 310 and, in particular theBluetooth transceiver 312 and NFC transceiver 316, to constantly monitorfor nearby Bluetooth and/or NFC-capable devices. In this regard, theuser device 50 may be in an “always on” state for identifying potentialdevices to pair with. However, many users may feel uncomfortable withthis always on state and prefer selectivity.

Accordingly, in another embodiment, the communication circuit 344 isstructured to selectively command or instruct the network interface 310and, in particular the Bluetooth transceiver 312 and NFC transceiver316, to monitor for, scan for, or otherwise search for nearby Bluetoothand/or NFC-capable devices (i.e., the financial institution computingdevice 30). Further, the communication circuit 344 may be structured toselectively activate which, of the Bluetooth transceiver 312 and the NFCtransceiver 316, is active (i.e., searching/ready to communicate withnearby devices).

The selectivity in commanding or instructing the network interface 310may be based on a user input received through the input/output circuit342. For example, the user 40 may enter the financial institution 10knowing that he/she would like to enroll with one or more products ofthe financial institution 10 (e.g., open a demand deposit account).Accordingly, the user 40 may provide an input to the user device 50 toactivate the account enrollment circuit 340 and, in particular, thecommunication circuit 344 to cause device scanning by the networkinterface 310. Because the enrollment process may include thetransmission of relatively personal or confidential data of the user 40,the aforementioned “input” may include one or more levels of security.For example, the input may include a predefined biometric input (e.g.,fingerprint scanner, retina scan, etc.). In another example, the inputmay include a pass code (e.g., a pattern; a numeric, alpha, oralpha-numeric password; etc.). In yet another example, the input mayinclude a combination of a pass code and a biometric. In this regard andbeneficially, triggering of the communication circuit 344 may berelatively secure.

The selectivity in commanding or instructing the network interface 310to scan for nearby devices may also be based on at least one of adetermined location of the user device 50 or a received input indicativeof a location of the user device 50. Responsive to the determinedlocation or the input indicating the user device 50 is in a locationindicative of a physical location of a financial institution, such asfinancial institution 10, the communication circuit 344 may instruct thenetwork interface 310 to scan for, e.g., nearby Bluetooth enableddevices. For example, via location data received by the location circuit320, the communication circuit 344 may determine or receive anindication that the user device 50 is in a financial institutionlocation and cause activation of at least one of the Bluetoothtransceiver 312 and the NFC transceiver 316.

In one embodiment, the communication circuit 344 is structured to permitdata flow from the personal information database 346 to the financialinstitution computing device 30 only in response to being activated. Inthis regard, the user 40 may utilize at least one of the Bluetoothtransceiver 312 and NFC transceiver 316 without activating or otherwiseusing the account enrollment circuit 340 (i.e., to keep data stored inthe personal information database 346 shielded from transmission oraccident transmission). In this regard, “activation” is defined as whentransmission from the personal information database 346 is allowed tooccur rather than determining when to initiate the network interface310, which is the definition of the term “selectivity” herein.

In one embodiment, the communication circuit 344 is structured tofacilitate scanning for nearby devices responsive to being activated.This embodiment may be useful if the user places the user device 50 in apower saving mode.

Activation may be based on any of the aforementioned selectivityprocesses. For example, activation may be based on reception of anexplicit user input to activate the account enrollment circuit 340. Asanother example, activation may be based on location data indicatingthat the user device 50 is within a physical location associated with afinancial institution. As yet another example, activation may be basedon the “tap” itself. For example, when the financial institution device30 is tapped with the user device 50, the communication circuit 344 mayenable the corresponding Bluetooth or NFC transceiver to maintain orestablish the communication channel 60.

As mentioned above, the communication circuit 344 is also structured toestablish and maintain the communication channel 60. As mentioned above,the communication channel 60 may include at least one a Bluetoothcommunication channel, a NFC communication channel, and/or a Bluetoothand NFC combined communication channel. Of course, use of thesecommunication protocols is not meant to be limiting as the principles ofthe present disclosure may be utilized with any short-range wirelesstechnology, where “short-range” may be defined as communication protocolrange less than or equal to that of the Bluetooth communicationprotocol.

During the communication session, personal information stored in thepersonal information database 346 may be retrieved and provided to thefinancial institution computing device 30. The financial institutioncomputing device 30 may utilize this information populate an accountregistration form or otherwise enroll the user 40 with a product of thefinancial institution 10. Accordingly, the exchange of information overthe communication channel 60 may include, but is not limited to, videos,files, and the like.

In one embodiment, the communication circuit 344 is preprogrammed withinformation required or typically required for certain financialproducts (e.g., enrollment for a mortgage, enrollment for a demanddeposit account, etc.). Accordingly, via an explicit user input receivedfrom the input/output circuit 342 and after establishment of thecommunication channel 60, the communication circuit 344 may search andretrieve the information required or typically required for the selectedproduct. In this regard, the account enrollment circuit 340 may beproactive in nature to increase the rate at which the user 40 becomesenrolled.

In addition to the communication protocols described above that may bethe communication channel 60, the communication circuit 344 may also bestructured to facilitate, arrange, or otherwise provide synchronousapplications. Alternatively, via the communication channel 60, thecommunication circuit 344 and corresponding financial institutioncomputing device 30 may cause initiation of synchronous applications onthe user device 50 and the financial institution computing device 30,respectively.

Referring now to FIG. 4, an example of the synced applications is shown,according to an example embodiment. The “synchronicity” of theapplications refers to the ability of an input on one graphical userinterface to be reflected on the synced other graphical user interface.In this regard, the attendant 20 and the user 40 may see in real time orsubstantially real time the personal or confidential information beingtransmitted and the enrollment process happening. For example and asshown in the synced application environment 400 of FIG. 4, the user 40may observe various personal information data points on the graphicaluser interface 410 of their user device 50. In particular, the user 40may observe their name 412, social security number 414, address 416,telephone number 418, provide an initial deposit amount 420, and eithercancel 422 or submit 424 this data to the attendant 20 of the financialinstitution computing device 30 to complete the enrollment process. Thatis to say, while the attendant may visualize this information, theinformation is not yet submitted for enrollment purposes until the userexplicitly submits the information. Similarly, the financial institutioncomputing device 30 may include a graphical user interface 450 thatprovides fields to observe the applicant's name 452, social securitynumber 454, address 456, telephone number 458, initial deposit amount460, and whether to request additional information 462. In this example,the user 40 is enrolling, registering, or signing-up for a demanddeposit account. Hence, the initial deposit fields 422, 462 provided onthe graphical user interfaces 410, 450.

In another example arrangement, the user device 50 serves as anintermediary between the personal information database 346 and financialinstitution computing device 30. In particular, a user 40 may haveprovided an indication that they were or are planning to enroll with thefinancial institution 10 to open up a checking account. After thecommunication channel 60 is established and rather than directlyproviding personal information for opening up a checking account, theaccount enrollment circuit 340 first provides the information to theuser device 50 to, e.g., the graphical user interface 410, for the user40 to observe, modify, add, or delete. Upon an approval received fromthe user 40, the account enrollment circuit 340 transmits the selectedpieces of personal information to the financial institution computingdevice 30. In this regard and while the account enrollment circuit 340may be preprogrammed with the information that is typically required toopen a checking account, the user 40 still serves as the final arbiterbefore transmission to the financial institution computing device 30.

Of course, in other embodiment, the data may be provided upon anestablishment of the communication channel 60. Some users may preferthis configuration if they are in a hurry and want to expedite theenrollment process even further.

After the transfer of data and either the success or unsuccessfulenrollment, cessation of the communication channel 60 may be caused orinitiated in a variety of manners. In one embodiment, a user 40 mayprovide an explicit input to affirmatively end the communication channel60. Alternatively, the communication circuit 344 may include a timerstructured to only maintain the communication channel 60 for apredetermined amount of time. Additionally and beneficially, because thecommunication channel 60 is structured as short-range channel (such asthe NFC or Bluetooth protocol), the communication channel 60 mayautomatically cease or end responsive to the user 40 moving outside ofthe transmission range of the user device 50.

In certain embodiments, the input/output circuit 342 may provide amessage (e.g., notification, alert, etc.) to the user device 50 toconfirm or deny cessation of the communication channel 60. According toanother embodiment and as an added layer of circuitry, the communicationcircuit 344 may facilitate providing a message (e.g., notification,alert, etc.) to a different user device for the user to verify cessationof the communication channel 60. In this regard, the communicationcircuit 344 may also provide the details (e.g., a report or summaryindicating the data that was exchanged, the product applied for, and anyother pertinent data) regarding the communication session to one or moreadditional locations relative to the user device 50. For example, thecommunication circuit 344 may, in addition to providing the details tothe user 40 via the account enrollment application 220, provide thedetails to a designated email account of the user. In another example,the communication circuit 344 may provide the details on a websiteprovided by the financial institution and accessible from a linktransmitted as either a text message or as an email message to the user.Some financial institutions may even require an additional input oncethe user access the report of the communication session to confirm ordeny the accuracy and finish the enrollment process.

Referring now to FIG. 5, a process 500 of onboarding or enrolling acustomer with a financial institution via a short-range communicationchannel is shown, according to an example embodiment. Because theprocess 500 may be implemented with the account enrollment circuit 340of FIGS. 1-3, reference may be made to various components of the accountenrollment circuit 340 and the computing system 200 in general to aidexplanation of process 500.

At process 502, a short range communication channel is established via atap exchange. The communication channel may have the same structure andconfiguration as mentioned above. Further and as also mentioned above, a“tap” exchange may include a pairing process to establish a short rangecommunication channel. In one embodiment, the tap may include aBluetooth communication pairing process. In this regard, the user of theuser device 50 and/or the attendant of the financial institutioncomputing device 30 may be required to affirmatively pair the userdevice with the financial computing device 30. Such pairing may alsoinclude providing a passcode to add an extra layer of security toprevent or substantially prevent unauthorized pairing with at least oneof the user device 50 and the financial institution computing device. Asalso mentioned above, the “tap” may also include a NFC tap. The NFC tapmay be useful due to its relatively shorter communication range toprevent unauthorized short range communication channels. Further, insome embodiments, the short range communication channel may include acombination of the NFC and Bluetooth protocol (e.g., an NFC tap toprovide authorization for the communication channel via the user deviceand the financial computing device followed by establishment of theBluetooth communication channel).

Before, during, or slightly after the tap (e.g., within a predefinedamount of time before or after the tap, such as one minute), varioussecurity protocols may be implemented. In particular, the communicationcircuit 344 may include selectivity to control when the networkinterface of the user device 50 is capable of establishing thecommunication channel. Further, the communication circuit 344 may alsobe adapted to only permit establishment of the communication channelafter activation of the communication circuit 344, wherein activationmay be based on receiving an explicit user input (e.g., a passcodereceived via the account enrollment client application 220),geographical data indicating that the user device is within a physicallocation associated with a financial institution, and/or some otherprocess as described herein above. As mentioned above, activation may berequired to enable the flow of data from the personal informationdatabase 346 to the financial institution computing device 30.

Process 502 may also include receiving a designation of a product thatthe user desires to utilize (i.e., signing-up, enrolling, or otherwiseon-boarding with). Such designation may dictate the selectivity and/oractivation processes as described above. For example, responsive todesignation of products that typically require relatively less personalinformation, the communication circuit 344 may cause the networkinterface to search for devices immediately, or, the communicationcircuit 344 may be activated immediately to allow the personalinformation to be retrieved and transmitted. However, responsive to thedesignation of a product that typically requires relatively more oruser-defined sensitive personal information, the communication circuit344 may require a passcode from the user prior to searching and/oractivation. Such processes may provide additional layers to securelystoring the user's personal information.

At process 504, a request for personal information is received. Therequest may be provided by the financial computing device 30 over thecommunication channel 60. In some embodiments, the request may bespecific to refer to the explicit types of personal information needed(e.g., social security number, etc.). In one embodiment, during process504, the attendant and user may utilize synced applications (see FIG.4), such that the user and attendant may see in real time or substantialreal time the data requested and the data being transmitted.

At process 506, authorization to transmit personal information isreceived. In one embodiment, the authorization may include a demarcationor designation of the specific types of personal information that istransmitted. For example, the user may, via the account enrollmentclient application 220, see a list of their person information stored inthe personal information database 346 and selectively pick specific datato transmit. In another embodiment, during, before, or afterestablishment of the communication channel, the user may provide aninput describing the financial institution product he/she is applying,registering, or otherwise enrolling with in order to utilize. As aresult, the communication circuit 344 may provide a predefined “package”of personal information typically associated with that product (e.g., ifthe product is a demand deposit account, the package may include anaddress, name, telephone number, social security number, and initialdeposit amount whereas if the product if a mortgage application, thepackage may include an address, telephone number, name, social securitynumber, down-payment amount, and pertinent tax information). In thisregard, providing of the package may speed-up the enrollment process.This configuration may be utilized when the user designates a desiredfinancial product, as described above in process 502.

At process 508, responsive to receiving authorization, personalinformation is transmitted via the short-range communication channel tothe financial institution computing device.

At process 510, a confirmation is received to complete the accountregistration. Process 510 may include generating and providing, via theaccount enrollment client application 220, a graphical user interface ofthe personal information provided along with an option for a user tosubmit, cancel, or modify the information. Responsive to submission, thefinancial institution computing device 30 may provide receiptconfirmation over the communication channel 60 to the user device 50.The receipt confirmation may indicate that the product application wassuccessfully submitted and that the financial institution will contactthe user shortly regarding the next steps. The receipt confirmation maybe stored in the personal information database 346, such that the usermay access the receipt confirmation at will.

In some embodiments, the financial institution computing device 30 maythen provide the relevant information to the financial institutioncomputing system 240 to finish the enrollment process. In otherembodiments, the enrollment process may be accomplished completely onthe financial institution computing device 30, such that the user device50 may be enrolled (or denied enrollment) immediately followingtransmission.

With the above in mind, an example of process 500 may be described asfollows. A user enters a physical location associated with a financialinstitution (e.g., a branch location). The location circuit providesdata to the account enrollment circuit confirming that the user iswithin the physical location associated with the financial institution.In response, the communication circuit 344 causes the network interface310 to begin scanning for financial institution computing devices (inthis regard, “selectivity” as defined herein is based on the locationdata). The user may then provide an input to indicate the type ofproduct that he/she is interested in utilizing (e.g., a checking and asavings account). At some time in the future, the user may tap theiruser device with the financial institution computing device to establisha short-range communication channel. In this example, the tap alsoactivates the communication circuit to begin to allow personalinformation to be retrieved and transmitted via the communicationcircuit 344. After the tap, the user may observe the type of data thatwill be transmitted and selectively allow or deny such transmission(i.e., the user device is serving as the intermediary between thefinancial institution computing device and the personal informationdatabase 346). After all the data is transmitted, the user device 50 mayreceive a receipt confirmation of enrollment with the checking account.Or, alternatively, the financial institution computing system 240 may berequired to perform additional processes prior to enrollment.

In either event, enrollment may occur relatively faster due to notneeding to physically fill-out various forms. Further, accuracy of thedata may be relatively higher because the data transmitted is previouslyprovided by the user such that the user can confirm the accuracy of thatdata (the attendant may make typographical errors). As a result, theuser may experience a relatively more pleasant enrolling process.

Technically, the systems, methods and apparatuses described herein maytransform operation of a user device, such as a smartphone, toselectively utilize one or more network interfaces (e.g., NFC,Bluetooth, etc.) to establish a secure or relatively securecommunication channel. Further, the user device may now serve as arepository or storage site for personal information of the user. Inanother embodiment, the personal information may be stored in the cloud.In either arrangement, the user may appreciate the flexibility providedby the systems herein to retain their personal and confidentialinformation relatively securely.

The embodiments described herein have been described with reference todrawings. The drawings illustrate certain details of specificembodiments that implement the systems, methods and programs describedherein. However, describing the embodiments with drawings should not beconstrued as imposing on the disclosure any limitations that may bepresent in the drawings.

It should be understood that no claim element herein is to be construedunder the provisions of 35 U.S.C. § 112(f), unless the element isexpressly recited using the phrase “means for.”

As used herein, the term “circuit” may include hardware structured toexecute the functions described herein. In some embodiments, eachrespective “circuit” may include machine-readable media for configuringthe hardware to execute the functions described herein. The circuit maybe embodied as one or more circuitry components including, but notlimited to, processing circuitry, network interfaces, peripheraldevices, input devices, output devices, sensors, etc. In someembodiments, a circuit may take the form of one or more analog circuits,electronic circuits (e.g., integrated circuits (IC), discrete circuits,system on a chip (SOCs) circuits, etc.), telecommunication circuits,hybrid circuits, and any other type of “circuit.” In this regard, the“circuit” may include any type of component for accomplishing orfacilitating achievement of the operations described herein. Forexample, a circuit as described herein may include one or moretransistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR,etc.), resistors, multiplexers, registers, capacitors, inductors,diodes, wiring, and so on).

The “circuit” may also include one or more dedicated processorscommunicatively coupled to one or more dedicated memory or memorydevices. In this regard, the one or more dedicated processors mayexecute instructions stored in the dedicated memory or may executeinstructions otherwise accessible to the one or more dedicatedprocessors. In some embodiments, the one or more dedicated processorsmay be embodied in various ways. The one or more dedicated processorsmay be constructed in a manner sufficient to perform at least theoperations described herein. In some embodiments, the one or morededicated processors may be shared by multiple circuits (e.g., circuit Aand circuit B may comprise or otherwise share the same processor which,in some example embodiments, may execute instructions stored, orotherwise accessed, via different areas of memory). Alternatively oradditionally, the one or more dedicated processors may be structured toperform or otherwise execute certain operations independent of one ormore co-processors. In other example embodiments, two or more processorsmay be coupled via a bus to enable independent, parallel, pipelined, ormulti-threaded instruction execution. Each processor may be implementedas one or more general-purpose processors, application specificintegrated circuits (ASICs), field programmable gate arrays (FPGAs),digital signal processors (DSPs), or other suitable electronic dataprocessing components structured to execute instructions provided bymemory. The one or more dedicated processors may take the form of asingle core processor, multi-core processor (e.g., a dual coreprocessor, triple core processor, quad core processor, etc.),microprocessor, etc.

Any foregoing references to currency or funds are intended to includefiat currencies, non-fiat currencies (e.g., precious metals), andmath-based currencies (often referred to as cryptocurrencies). Examplesof math-based currencies include Bitcoin, Litecoin, Dogecoin, and thelike.

It should be noted that although the diagrams herein may show a specificorder and composition of method steps, it is understood that the orderof these steps may differ from what is depicted. For example, two ormore steps may be performed concurrently or with partial concurrence.Also, some method steps that are performed as discrete steps may becombined, steps being performed as a combined step may be separated intodiscrete steps, the sequence of certain processes may be reversed orotherwise varied, and the nature or number of discrete processes may bealtered or varied. The order or sequence of any element or apparatus maybe varied or substituted according to alternative embodiments.Accordingly, all such modifications are intended to be included withinthe scope of the present disclosure as defined in the appended claims.

The foregoing description of embodiments has been presented for purposesof illustration and description. It is not intended to be exhaustive orto limit the disclosure to the precise form disclosed, and modificationsand variations are possible in light of the above teachings or may beacquired from this disclosure. The embodiments were chosen and describedin order to explain the principals of the disclosure and its practicalapplication to enable one skilled in the art to utilize the variousembodiments and with various modifications as are suited to theparticular use contemplated. Other substitutions, modifications, changesand omissions may be made in the design, operating conditions andarrangement of the embodiments without departing from the scope of thepresent disclosure as expressed in the appended claims.

What is claimed:
 1. A computing device associated with a financialinstitution, the computing device comprising: a network interfaceenabling the computing device to exchange information over a network;one or more processors; and non-transitory machine-readable mediastoring instructions that, when executed by the one or more processors,cause the one or more processors to perform operations comprising:establishing a short-range communication channel with a user deviceassociated with a user based on a tap exchange; receiving personalinformation from the user device over the short-range communicationchannel, the personal information associated with an enrollment of theuser with a product of the financial institution; and providing thepersonal information to a computing system associated with the financialinstitution to enroll the user with the product.
 2. The computing deviceof claim 1, wherein the short-range communication channel is at leastone of a Bluetooth communication protocol or a near-field communicationprotocol.
 3. The computing device of claim 1, wherein the tap exchangeis a near-field communication tap, and wherein the short-rangecommunication channel is a Bluetooth communication protocol.
 4. Thecomputing device of claim 1, wherein the personal information isencrypted.
 5. The computing device of claim 1, the operations furthercomprising providing a receipt confirmation to the user deviceresponsive to providing the personal information to the computingsystem, the receipt confirmation indicating that an application for theenrollment of the user with the product was successfully submitted tothe financial institution.
 6. The computing device of claim 1, whereinthe product includes at least one of a demand deposit account, amortgage application, a certificate of deposit account, a money marketaccount, an individual retirement account, or a loan application.
 7. Thecomputing device of claim 1, the operations further comprising providinga data request to the user device responsive to establishing theshort-range communication channel, the data request indicatingparticular personal information required to enroll the user with theproduct, wherein the personal information received from the user devicecomprises the particular personal information.
 8. The computing deviceof claim 1, wherein the enrollment is a first-time enrollment processfor the user with the financial institution.
 9. The computing device ofclaim 1, wherein the computing device further comprises a graphical userinterface (GUI) configured to display the personal information receivedover the short-range communication channel, the GUI updated as newpersonal information is received over the short-range communicationchannel.
 10. A method for enrolling a user with a product of a financialinstitution, the method comprising: establishing, by a computing deviceassociated with the financial institution, a short-range communicationchannel between the computing device and a user device associated withthe user based on a tap exchange; receiving, by the computing device,personal information from the user device over the short-rangecommunication channel, the personal information associated with anenrollment of the user with the product of the financial institution;and providing, by the computing device, the personal information to acomputing system associated with the financial institution to enroll theuser with the product.
 11. The method of claim 10, wherein theshort-range communication channel is at least one of a Bluetoothcommunication protocol or a near-field communication protocol.
 12. Themethod of claim 10, wherein the tap exchange is a near-fieldcommunication tap, and wherein the short-range communication channel isof a Bluetooth communication protocol.
 13. The method of claim 10,wherein the personal information is encrypted.
 14. The method of claim10, further comprising providing, by the computing device, a receiptconfirmation to the user device responsive to providing the personalinformation to the computing system, the receipt confirmation indicatingthat an application for the enrollment of the user with the product wassuccessfully submitted to the financial institution.
 15. The method ofclaim 10, wherein the product includes at least one of a demand depositaccount, a mortgage application, a certificate of deposit account, amoney market account, an individual retirement account, or a loanapplication.
 16. The method of claim 10, further comprising providing,by the computing device, a data request to the user device responsive toestablishing the short-range communication channel, the data requestindicating particular personal information required to enroll the userwith the product, wherein the personal information received from theuser device comprises the particular personal information.
 17. Themethod of claim 10, wherein the enrollment is a first-time enrollmentprocess for the user with the financial institution.
 18. The method ofclaim 10, further comprising: displaying, by the computing device, thepersonal information received over the short-range communication channelon a graphical user interface (GUI) of the computing device; andupdating, by the computing device, the GUI as new personal informationis received over the short-range communication channel.
 19. A method forenrolling a user with a product of a financial institution, the methodcomprising: establishing, by a computing device associated with thefinancial institution, an encrypted short-range communication channelbetween the computing device and a user device associated with the userbased on a tap exchange; receiving, by the computing device, personalinformation from the user device over the encrypted short-rangecommunication channel, the personal information associated with anenrollment of the user with the product of the financial institution;populating, by the computing device, an account registration form withthe personal information; and providing, by the computing device, theaccount registration form to a computing system associated with thefinancial institution to enroll the user with the product.
 20. Themethod of claim 19, wherein: the account registration form is providedto the computing system responsive to receiving an approval message fromthe user device indicating that the user confirmed an accuracy of thepersonal information; and the encrypted short-range communicationchannel is at least one of a Bluetooth communication protocol or anear-field communication protocol.